Skip to content

[No QA][HR Import] Add MergeHRApprovalModePage #91202

Merged
grgia merged 14 commits into
Expensify:mainfrom
software-mansion-labs:feat/merge-hr-approval-mode-page
May 21, 2026
Merged

[No QA][HR Import] Add MergeHRApprovalModePage #91202
grgia merged 14 commits into
Expensify:mainfrom
software-mansion-labs:feat/merge-hr-approval-mode-page

Conversation

@jmusial
Copy link
Copy Markdown
Contributor

@jmusial jmusial commented May 20, 2026

Explanation of Change

This PR adds MergeHRApprovalModePage to the Merge dev flows. It also unifies Gustos and Merge
Approval Mode pages.

Fixed Issues

$ #90602
PROPOSAL:

Tests

Pre requisites:

  1. Have a workspace with mergeHRConnections flag on
  2. Have a provider coonected (ex. Bamboo)

Steps:

  1. Go to Workspaces -> HR
  2. Click Approval Mode
  3. Side panel openes, change the approval mode
  4. New approval mode is set.

Offline tests

Same as test steps.

QA Steps

N/A

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Screen.Recording.2026-05-21.at.11.44.35.mov
MacOS: Chrome / Safari
Screen.Recording.2026-05-21.at.11.43.00.mov

@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 20, 2026

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

@codecov
Copy link
Copy Markdown

codecov Bot commented May 20, 2026

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/pages/workspace/hr/HRProviderCard.tsx 0.00% <0.00%> (ø)
...pages/workspace/hr/gusto/GustoApprovalModePage.tsx 0.00% <0.00%> (ø)
...ges/workspace/hr/merge/MergeHRApprovalModePage.tsx 0.00% <0.00%> (ø)
src/pages/workspace/hr/HRApprovalModePageBase.tsx 0.00% <0.00%> (ø)
... and 9 files with indirect coverage changes

@jmusial
Copy link
Copy Markdown
Contributor Author

jmusial commented May 21, 2026

@grgia @cristipaval can I have a polyglot parrot triggered here please ?

@jmusial jmusial marked this pull request as ready for review May 21, 2026 10:06
@jmusial jmusial requested review from a team as code owners May 21, 2026 10:06
@melvin-bot melvin-bot Bot requested review from bernhardoj and flaviadefaria and removed request for a team May 21, 2026 10:06
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 21, 2026

@bernhardoj Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

<OfflineWithFeedback
pendingAction={card.config?.pendingFields?.approvalMode}
errors={card.config?.errorFields?.approvalMode}
onClose={() => clearMergeHRErrorField(policy?.id)}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ CONSISTENCY-6 (docs)

The clearMergeHRErrorField function requires both policyID and provider parameters, but only policy?.id is passed here. Since provider will be undefined, the function will early-return without clearing the error, making the onClose callback a silent no-op.

Pass the provider name as the second argument. The card object likely has a provider identifier available:

onClose={() => clearMergeHRErrorField(policy?.id, card.providerName)}

Reviewed at: d0b9302 | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jmusial this one is always early returning

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d0b930247a

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

<OfflineWithFeedback
pendingAction={card.config?.pendingFields?.approvalMode}
errors={card.config?.errorFields?.approvalMode}
onClose={() => clearMergeHRErrorField(policy?.id)}
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Pass provider when clearing approval mode errors

onClose calls clearMergeHRErrorField(policy?.id) without a provider, but clearMergeHRErrorField now returns early unless both policyID and provider are present. In the approval-mode error state, dismissing the OfflineWithFeedback error will therefore no-op and the error remains stuck in Onyx/UI. This affects any HR approval mode update failure where the user tries to clear the error.

Useful? React with 👍 / 👎.

@grgia grgia self-requested a review May 21, 2026 10:20
@OSBotify

This comment has been minimized.

@grgia grgia requested a review from cristipaval May 21, 2026 11:20
@OSBotify
Copy link
Copy Markdown
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/es.ts b/src/languages/es.ts
index f57ef47b..80459018 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -6268,7 +6268,7 @@ ${amount} para ${merchant} - ${date}`,
             syncError: (providerName: string) => `No se puede conectar con ${providerName}`,
             connectionDescription: (providerName: string) => `Conecta ${providerName} para mantener sincronizadas las aprobaciones de empleados con tu espacio de trabajo.`,
             approvalMode: 'Modo de aprobación',
-            providerApprovalMode: (providerName: string) => `Modo de aprobación de ${providerName}`,
+            providerApprovalMode: (providerName: string) => `modo de aprobación de ${providerName}`,
             finalApprover: 'Aprobador final',
             notSet: 'No configurado',
             approvalModeDescription: (providerName: string) => `Los miembros y gerentes están configurados para sincronizarse con ${providerName}.`,
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 26ed6655..e4104cff 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -7176,7 +7176,7 @@ Ajoutez davantage de règles de dépenses pour protéger la trésorerie de l’e
             syncError: (providerName: string) => `Impossible de se connecter à ${providerName}`,
             connectionDescription: (providerName: string) => `Connectez ${providerName} pour synchroniser les approbations des employés avec votre espace de travail.`,
             approvalMode: "Mode d'approbation",
-            providerApprovalMode: (providerName: string) => `Mode d'approbation ${providerName}`,
+            providerApprovalMode: (providerName: string) => `Mode d’approbation ${providerName}`,
             finalApprover: 'Approbateur final',
             notSet: 'Non défini',
             approvalModeDescription: (providerName: string) => `Les membres et les responsables sont configurés pour se synchroniser avec ${providerName}.`,
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 26204ac3..6d100d4d 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -7059,7 +7059,7 @@ ${reportName}
             syncError: (providerName: string) => `${providerName}に接続できません`,
             connectionDescription: (providerName: string) => `${providerName}を接続して、従業員の承認をワークスペースと同期させましょう。`,
             approvalMode: '承認モード',
-            providerApprovalMode: (providerName: string) => `${providerName}の承認モード`,
+            providerApprovalMode: (providerName: string) => `${providerName} 承認モード`,
             finalApprover: '最終承認者',
             notSet: '未設定',
             approvalModeDescription: (providerName: string) => `メンバーとマネージャーは ${providerName} と同期するように設定されています。`,
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 58689355..3d6d04a0 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -6932,7 +6932,7 @@ ${reportName}
             syncError: (providerName: string) => `无法连接到 ${providerName}`,
             connectionDescription: (providerName: string) => `连接 ${providerName},以在您的工作区中同步员工审批。`,
             approvalMode: '审批模式',
-            providerApprovalMode: (providerName: string) => `${providerName}审批模式`,
+            providerApprovalMode: (providerName: string) => `${providerName} 审批模式`,
             finalApprover: '最终审批人',
             notSet: '未设置',
             approvalModeDescription: (providerName: string) => `成员和管理员已设置为与 ${providerName} 同步。`,

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

View workflow run

@github-actions
Copy link
Copy Markdown
Contributor

🚧 @grgia has triggered a test Expensify/App build. You can view the workflow run here.

@grgia
Copy link
Copy Markdown
Contributor

grgia commented May 21, 2026

@jmusial will need to merge main

@github-actions

This comment has been minimized.

Comment thread src/pages/workspace/hr/HRProviderCard.tsx Outdated
@grgia grgia mentioned this pull request May 21, 2026
50 tasks
Comment thread src/libs/actions/connections/MergeHR.ts Outdated
export {syncMergeHR, updateMergeHRApprovalMode, updateMergeHRFinalApprover};
type HRProviderName = TupleToUnion<typeof CONST.POLICY.CONNECTIONS.HR_CONNECTION_NAMES>;

function clearMergeHRErrorField(policyID?: string, provider?: HRProviderName) {
Copy link
Copy Markdown
Contributor

@bernhardoj bernhardoj May 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think instead of making the params optional, we should update the type to be undefined-able.

Suggested change
function clearMergeHRErrorField(policyID?: string, provider?: HRProviderName) {
function clearMergeHRErrorField(policyID: string | undefined, provider: HRProviderName | undefined) {

This will prevent unintended bug like the on caught by AI here

Comment thread src/libs/actions/connections/MergeHR.ts Outdated
connections: {
[provider]: {
config: {
errorFields: null,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This clears the whole errorFields. If we have both approvalMode and finalApprover errorFields, clearing one of them will clear both.

@bernhardoj
Copy link
Copy Markdown
Contributor

Is there a test account I can use to connect?

@mhawryluk
Copy link
Copy Markdown
Contributor

Is there a test account I can use to connect?

yes, I sent it to you on Slack just now

@jmusial jmusial requested a review from grgia May 21, 2026 14:26
@bernhardoj
Copy link
Copy Markdown
Contributor

bernhardoj commented May 21, 2026

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
android.mp4
Android: mWeb Chrome
android.mweb.mp4
iOS: HybridApp
ios.mp4
iOS: mWeb Safari
ios.mweb.mp4
MacOS: Chrome / Safari
web.mp4

@bernhardoj
Copy link
Copy Markdown
Contributor

The confirmation modal is missing the confirmation text on native.

image

@bernhardoj
Copy link
Copy Markdown
Contributor

I can't seem to connect to the HR provider on iOS 🤔

ioss.mp4

@jmusial
Copy link
Copy Markdown
Contributor Author

jmusial commented May 21, 2026

The confirmation modal is missing the confirmation text on native.

Fixed
image

@jmusial
Copy link
Copy Markdown
Contributor Author

jmusial commented May 21, 2026

I can't seem to connect to the HR provider on iOS 🤔

ioss.mp4

yup, we're aware of the issue, it will be solved here

Comment thread src/pages/workspace/hr/merge/MergeHRApprovalModePage.tsx
@melvin-bot melvin-bot Bot requested a review from grgia May 21, 2026 15:04
@grgia grgia merged commit 01d396c into Expensify:main May 21, 2026
31 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

🚧 @grgia has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify
Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/grgia in version: 9.3.79-1 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Bundle Size Analysis (Sentry):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants